Skip to main content
POST
Add capex proposals to any plan, and correct proposals on any plan, from one spreadsheet. p_payload is {"lines"…

Headers

Prefer
enum<string>

Preference

Available options:
params=single-object

Body

Add capex proposals to any plan, and correct proposals on any plan, from one spreadsheet. p_payload is {"lines": [...]}, a row of the file each, at most 2,000, read exactly as import_capex_plan_lines reads a row, with one key more: plan, the code or name of a capex plan. A row giving the Proposal ID (scheme_code) of a proposal on a plan you can see corrects that proposal on its plan; a Plan given beside it must be that plan, since an upload does not move a proposal, and must say which where a proposal and the copy a consolidation made of it share the ID. A row with no Proposal ID, or one no proposal you can see has, adds a new proposal to the plan its Plan names, by code first and then by name, as import_capex_plan_lines adds one. Proposals the file does not mention are left as they are. Every rule import_capex_plan_lines holds a row to applies, plan by plan, and a plan that cannot be changed at all is a problem on each of its rows. A file that adds a proposal needs finance.capex_scheme.create, and one that corrects a proposal finance.capex_scheme.edit. Writes everything or nothing across all the plans, and only when p_dry_run is false. Returns ok, dry_run, written, problems and notices (each a row and a message, in the file's order), lines_created and lines_updated.

p_payload
string<jsonb>
required
p_dry_run
boolean<boolean>

Response

200

OK